Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 574b5464bbefea64c6fa6da61bcf0697a85369db353438c794d71f806f0e2587

Tx prefix hash: aa64a2908772495c1a5142c149a2790e42d37d893fc6cd6314b6c69c2e6ad8e5
Tx public key: b63e227e1346f2cc528f620a4fc753df189902b80f1775d70d29ad9e97a863af
Timestamp: 1723813700 Timestamp [UCT]: 2024-08-16 13:08:20 Age [y:d:h:m:s]: 00:285:19:18:36
Block: 1089175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204191 RingCT/type: yes/0
Extra: 01b63e227e1346f2cc528f620a4fc753df189902b80f1775d70d29ad9e97a863af02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8367189ad03a5b87b11d825f661813d1001605be6bada16f5476c091aa1e6faf 0.600000000000 1563794 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": 1089185, "vin": [ { "gen": { "height": 1089175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8367189ad03a5b87b11d825f661813d1001605be6bada16f5476c091aa1e6faf" } } ], "extra": [ 1, 182, 62, 34, 126, 19, 70, 242, 204, 82, 143, 98, 10, 79, 199, 83, 223, 24, 153, 2, 184, 15, 23, 117, 215, 13, 41, 173, 158, 151, 168, 99, 175, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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