Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1a1254baa5979c8dd9430e3ed707511bf21dfd17b26a37ad9b05be2af268418

Tx prefix hash: bf5461b009ab8eb39a8a8462f2695ba29a1e9fa9cbdea203eaeb0fdc240c6544
Tx public key: 38aa66cad9936aa2fd079974ae9aef6cf2a188a415c6957179e7982b35f5a507
Timestamp: 1724528176 Timestamp [UCT]: 2024-08-24 19:36:16 Age [y:d:h:m:s]: 00:220:21:40:57
Block: 1095117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157716 RingCT/type: yes/0
Extra: 0138aa66cad9936aa2fd079974ae9aef6cf2a188a415c6957179e7982b35f5a507021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75121ab3e828c27311dddea343c25272039dc41b678cc8b666bfd9a670cc3ffc 0.600000000000 1570260 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": 1095127, "vin": [ { "gen": { "height": 1095117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75121ab3e828c27311dddea343c25272039dc41b678cc8b666bfd9a670cc3ffc" } } ], "extra": [ 1, 56, 170, 102, 202, 217, 147, 106, 162, 253, 7, 153, 116, 174, 154, 239, 108, 242, 161, 136, 164, 21, 198, 149, 113, 121, 231, 152, 43, 53, 245, 165, 7, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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