Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa556022c3bee8d492446e3bc2cc0d0ce3c15427fec844eed89362db9d7f659c

Tx prefix hash: 571d0f1ab7bfef5d7b8f632f7df47e9405cc3bfda77e1c5a7d605e6912ed711f
Tx public key: 7f4d3ac1aa4d036360b2aec96348879c0f1baaa29312519ea713014ac13c3a0e
Timestamp: 1746689156 Timestamp [UCT]: 2025-05-08 07:25:56 Age [y:d:h:m:s]: 00:190:16:11:10
Block: 1278295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133980 RingCT/type: yes/0
Extra: 017f4d3ac1aa4d036360b2aec96348879c0f1baaa29312519ea713014ac13c3a0e0211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dd06d76aa9aed462255eef37e47df35ad70d56cccbf1e11d8b829a9d6c685a4 0.600000000000 1765660 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": 1278305, "vin": [ { "gen": { "height": 1278295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dd06d76aa9aed462255eef37e47df35ad70d56cccbf1e11d8b829a9d6c685a4" } } ], "extra": [ 1, 127, 77, 58, 193, 170, 77, 3, 99, 96, 178, 174, 201, 99, 72, 135, 156, 15, 27, 170, 162, 147, 18, 81, 158, 167, 19, 1, 74, 193, 60, 58, 14, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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