Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6045c280d8d7a9ade7e7a3f9e880e5a7242769d5fcf6b7634c461103bea5ed8c

Tx prefix hash: eb91f0ed689f1569a0ff9e638faf646e7aad207fab60812c2911ee97215b2c2c
Tx public key: fafd9b85d97d669a0929e402b47295e6810cf8f2e1469a7921e6477f189682b2
Timestamp: 1702797054 Timestamp [UCT]: 2023-12-17 07:10:54 Age [y:d:h:m:s]: 01:337:21:12:03
Block: 914931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500348 RingCT/type: yes/0
Extra: 01fafd9b85d97d669a0929e402b47295e6810cf8f2e1469a7921e6477f189682b202110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94a3b7f4355a75be969c18bf92f38ccb0f3d9f12d00e2b7683f83a914df3f762 0.600000000000 1372291 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": 914941, "vin": [ { "gen": { "height": 914931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94a3b7f4355a75be969c18bf92f38ccb0f3d9f12d00e2b7683f83a914df3f762" } } ], "extra": [ 1, 250, 253, 155, 133, 217, 125, 102, 154, 9, 41, 228, 2, 180, 114, 149, 230, 129, 12, 248, 242, 225, 70, 154, 121, 33, 230, 71, 127, 24, 150, 130, 178, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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