Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5139ccab69e1531a3744d549f038c3d3107293af68c501df10303ff4aac409d8

Tx prefix hash: a48da211b335a0bd2911f048d893a1f9e380fdbedc3b67579a78780069862fd4
Tx public key: d3b7f067217c4cbfe2ba7c2ebfddff92c3dd4f8c953290cdb627150b11ee60ac
Timestamp: 1751398739 Timestamp [UCT]: 2025-07-01 19:38:59 Age [y:d:h:m:s]: 00:137:06:49:11
Block: 1316743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96336 RingCT/type: yes/0
Extra: 01d3b7f067217c4cbfe2ba7c2ebfddff92c3dd4f8c953290cdb627150b11ee60ac021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2857b3613ad120a801f31f3241d927835a4126a2100007c3a6c2b3c12d104160 0.600000000000 1804406 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": 1316753, "vin": [ { "gen": { "height": 1316743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2857b3613ad120a801f31f3241d927835a4126a2100007c3a6c2b3c12d104160" } } ], "extra": [ 1, 211, 183, 240, 103, 33, 124, 76, 191, 226, 186, 124, 46, 191, 221, 255, 146, 195, 221, 79, 140, 149, 50, 144, 205, 182, 39, 21, 11, 17, 238, 96, 172, 2, 17, 0, 0, 0, 1, 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