Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77f0533a9146c39a5af15d93475b7144ba7e3a9202b3fd999d13ae1388636258

Tx prefix hash: ed21bccbb81d68526a0fccad3ef69dec10cf62afe4260b3170cc3d4d6f7d5836
Tx public key: 2c183ba020b7a916c9531297c26742afc6f03ccfaf5c0aeced78091524632a5e
Timestamp: 1749978730 Timestamp [UCT]: 2025-06-15 09:12:10 Age [y:d:h:m:s]: 00:151:19:33:48
Block: 1305438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106274 RingCT/type: yes/0
Extra: 012c183ba020b7a916c9531297c26742afc6f03ccfaf5c0aeced78091524632a5e021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f22b5940ca4ce9bd8b5b62a14bfb58c5f5db05f1d24fb352d5efb796374d2e0e 0.600000000000 1793039 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": 1305448, "vin": [ { "gen": { "height": 1305438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f22b5940ca4ce9bd8b5b62a14bfb58c5f5db05f1d24fb352d5efb796374d2e0e" } } ], "extra": [ 1, 44, 24, 59, 160, 32, 183, 169, 22, 201, 83, 18, 151, 194, 103, 66, 175, 198, 240, 60, 207, 175, 92, 10, 236, 237, 120, 9, 21, 36, 99, 42, 94, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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