Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3673ff264da90821d1a70229bd28713660558e416e17453e70a5f79819de118

Tx prefix hash: 282e28f6f9097c59219579eb5dfe86d6afa672479a5614ef3fe743ab0a7866b2
Tx public key: 8ac9ab1f43c4fb212de719ef1c78a57ed6c1a25783ce0fd2853c8b2c52eb4236
Timestamp: 1749486936 Timestamp [UCT]: 2025-06-09 16:35:36 Age [y:d:h:m:s]: 00:154:03:09:08
Block: 1301469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107828 RingCT/type: yes/0
Extra: 018ac9ab1f43c4fb212de719ef1c78a57ed6c1a25783ce0fd2853c8b2c52eb423602110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e732fdcce699495a9a45ae40b6c6a920c4e546afdcc28efb7a13b76e24a7603c 0.600000000000 1789028 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": 1301479, "vin": [ { "gen": { "height": 1301469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e732fdcce699495a9a45ae40b6c6a920c4e546afdcc28efb7a13b76e24a7603c" } } ], "extra": [ 1, 138, 201, 171, 31, 67, 196, 251, 33, 45, 231, 25, 239, 28, 120, 165, 126, 214, 193, 162, 87, 131, 206, 15, 210, 133, 60, 139, 44, 82, 235, 66, 54, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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