Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95a84d80b9777bffb582406f80928794174cc76f4a577f2a171e3929ffe62ad9

Tx prefix hash: 5812cc5d3ae2f50cb3d0e013b5e008940351fbabc00276d2351183c2fcb2fb79
Tx public key: 5cb3098c2f3e0c08602c99405a0445588718a0d10179664bf6350e1872c29c4e
Timestamp: 1741080625 Timestamp [UCT]: 2025-03-04 09:30:25 Age [y:d:h:m:s]: 00:095:22:31:32
Block: 1231865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68630 RingCT/type: yes/0
Extra: 015cb3098c2f3e0c08602c99405a0445588718a0d10179664bf6350e1872c29c4e02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f059ea1ae2fc07061d8e38ce4aafbb0847fca0726474de5bb7aa6450f9cbfbeb 0.600000000000 1718776 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": 1231875, "vin": [ { "gen": { "height": 1231865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f059ea1ae2fc07061d8e38ce4aafbb0847fca0726474de5bb7aa6450f9cbfbeb" } } ], "extra": [ 1, 92, 179, 9, 140, 47, 62, 12, 8, 96, 44, 153, 64, 90, 4, 69, 88, 135, 24, 160, 209, 1, 121, 102, 75, 246, 53, 14, 24, 114, 194, 156, 78, 2, 17, 0, 0, 0, 10, 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