Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17aa18a6e14fc9ba2859c59bf3726c07fc0d7bd4f2176431953342a391a475ab

Tx prefix hash: d786be7e37057cbcf52c97e5fd251bf7e83063393a25d741d12eb57d6ffaa1c2
Tx public key: 0fee89d619f7deced71f8f9db1767e7d56d29449263cb997d324fc66e68decbc
Timestamp: 1719508548 Timestamp [UCT]: 2024-06-27 17:15:48 Age [y:d:h:m:s]: 00:351:17:26:27
Block: 1053469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251316 RingCT/type: yes/0
Extra: 010fee89d619f7deced71f8f9db1767e7d56d29449263cb997d324fc66e68decbc02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51f1f00e901d5ae2a24ca78b901caf8e2c8f60606c4db33a67c3b0f05c93a606 0.600000000000 1523816 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": 1053479, "vin": [ { "gen": { "height": 1053469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51f1f00e901d5ae2a24ca78b901caf8e2c8f60606c4db33a67c3b0f05c93a606" } } ], "extra": [ 1, 15, 238, 137, 214, 25, 247, 222, 206, 215, 31, 143, 157, 177, 118, 126, 125, 86, 210, 148, 73, 38, 60, 185, 151, 211, 36, 252, 102, 230, 141, 236, 188, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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