Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2950251ff83458262c71b93bd0351b7b367d1874c314c852de715707b5707f9

Tx prefix hash: fa5805ba293bb7e8d32aa786283e229ada6265384517debe3dc6fb78203abfbb
Tx public key: 47047b37b1d79352f0b1017f2ecfe1fcdfa8195e51fa2aa45e55c62a058dbfb5
Timestamp: 1722842521 Timestamp [UCT]: 2024-08-05 07:22:01 Age [y:d:h:m:s]: 00:080:03:55:31
Block: 1081117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57393 RingCT/type: yes/0
Extra: 0147047b37b1d79352f0b1017f2ecfe1fcdfa8195e51fa2aa45e55c62a058dbfb5021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b7a9d80561f10dd379be9285bb7f53a638740036ec16cf7b51c8ae253640dd1 0.600000000000 1554738 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": 1081127, "vin": [ { "gen": { "height": 1081117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b7a9d80561f10dd379be9285bb7f53a638740036ec16cf7b51c8ae253640dd1" } } ], "extra": [ 1, 71, 4, 123, 55, 177, 215, 147, 82, 240, 177, 1, 127, 46, 207, 225, 252, 223, 168, 25, 94, 81, 250, 42, 164, 94, 85, 198, 42, 5, 141, 191, 181, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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