Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a0b85e9415d1ecd244b3af44716a2e0797a5f96585a742e5569b42a3206a79e4

Tx prefix hash: 49b049eab4cd339085152c5aee1b8cc15cee4688931e3960db12f36372441c50
Tx public key: 9fdd87c13c7dbdb5c76135207bbaf1d82d5bbb4463bde3465cbf90e6b7d54540
Timestamp: 1711921731 Timestamp [UCT]: 2024-03-31 21:48:51 Age [y:d:h:m:s]: 01:021:21:18:24
Block: 990600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276594 RingCT/type: yes/0
Extra: 019fdd87c13c7dbdb5c76135207bbaf1d82d5bbb4463bde3465cbf90e6b7d545400211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ccc2362dcde231a68cbdf4ce44238a00dd37ddd6d05590d7a210f1eb47f14b9 0.600000000000 1450924 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 990610, "vin": [ { "gen": { "height": 990600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ccc2362dcde231a68cbdf4ce44238a00dd37ddd6d05590d7a210f1eb47f14b9" } } ], "extra": [ 1, 159, 221, 135, 193, 60, 125, 189, 181, 199, 97, 53, 32, 123, 186, 241, 216, 45, 91, 187, 68, 99, 189, 227, 70, 92, 191, 144, 230, 183, 213, 69, 64, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8