Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f0b9597d46237211a12122fa31b916b7368c4b8f410ef3ab1008968dca4ad11

Tx prefix hash: 46f6db7f8116d45bc757ae9ff201fc94876a9770ce578edb10c7ab343703bf8e
Tx public key: a290d2e35a1f317c17d25f6ea085f593deae192cab4d338d575cefc19756e3b8
Timestamp: 1729339624 Timestamp [UCT]: 2024-10-19 12:07:04 Age [y:d:h:m:s]: 00:019:09:28:41
Block: 1134979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13817 RingCT/type: yes/0
Extra: 01a290d2e35a1f317c17d25f6ea085f593deae192cab4d338d575cefc19756e3b8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c66322af40501607a70e8ac062ef66f7128fac5f110a3678260b1af85ea16059 0.600000000000 1618306 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": 1134989, "vin": [ { "gen": { "height": 1134979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c66322af40501607a70e8ac062ef66f7128fac5f110a3678260b1af85ea16059" } } ], "extra": [ 1, 162, 144, 210, 227, 90, 31, 49, 124, 23, 210, 95, 110, 160, 133, 245, 147, 222, 174, 25, 44, 171, 77, 51, 141, 87, 92, 239, 193, 151, 86, 227, 184, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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