Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46133f4eae6add4365e837f14e0582a7ca351e5655bf62c91e7958f6ac180c0d

Tx prefix hash: f7e1edd66ab06538b3c901c9ea1f507147980d3fc2fd033768150f1a80bbd7d4
Tx public key: aa9a59353b0ca9b42695824d7ca3901c54d889105153c6422c5e60c919fcb4ec
Timestamp: 1754680410 Timestamp [UCT]: 2025-08-08 19:13:30 Age [y:d:h:m:s]: 00:099:13:23:14
Block: 1343014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70245 RingCT/type: yes/0
Extra: 01aa9a59353b0ca9b42695824d7ca3901c54d889105153c6422c5e60c919fcb4ec02110000000bad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67467513fee162c9d4d0d7cea60bca4c1c06d5b7d1a93640b984a5e549699d5d 0.600000000000 1830849 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": 1343024, "vin": [ { "gen": { "height": 1343014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67467513fee162c9d4d0d7cea60bca4c1c06d5b7d1a93640b984a5e549699d5d" } } ], "extra": [ 1, 170, 154, 89, 53, 59, 12, 169, 180, 38, 149, 130, 77, 124, 163, 144, 28, 84, 216, 137, 16, 81, 83, 198, 66, 44, 94, 96, 201, 25, 252, 180, 236, 2, 17, 0, 0, 0, 11, 173, 121, 72, 208, 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