Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a6f06cf6be8b88aeb527f154641b1e3e8b14306bc433ace1194a3c4e02983b8

Tx prefix hash: 601b980b4d9cd90d4ccd00006d4ea8d2dbec87eb742445e89c4ae5166d2eaea0
Tx public key: 5023735ad65ba5bf94564287dc70eacd2016a1c04e2af20f607617f524d73ad0
Timestamp: 1757425783 Timestamp [UCT]: 2025-09-09 13:49:43 Age [y:d:h:m:s]: 00:118:09:58:32
Block: 1364759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84775 RingCT/type: yes/0
Extra: 015023735ad65ba5bf94564287dc70eacd2016a1c04e2af20f607617f524d73ad002110000000ab2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91e24af86b7aae213252756968cafcfb6b2fdcf39b812826d089a5e502c92f9b 0.600000000000 1852798 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": 1364769, "vin": [ { "gen": { "height": 1364759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91e24af86b7aae213252756968cafcfb6b2fdcf39b812826d089a5e502c92f9b" } } ], "extra": [ 1, 80, 35, 115, 90, 214, 91, 165, 191, 148, 86, 66, 135, 220, 112, 234, 205, 32, 22, 161, 192, 78, 42, 242, 15, 96, 118, 23, 245, 36, 215, 58, 208, 2, 17, 0, 0, 0, 10, 178, 247, 132, 196, 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