Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8e3bee2e0fd0dd35c4dd1cb5863dca29686bbf458a1892f05abd9120515a114

Tx prefix hash: 1705f5e4569f29a0f7e47b61c26b686224a82738ed1679c1f717429f37e0654a
Tx public key: 7d9acd60876973d8cb7ae8a00b3b18ed4cfbb6cae6de972e9e8c5a609eeae0ac
Timestamp: 1718814723 Timestamp [UCT]: 2024-06-19 16:32:03 Age [y:d:h:m:s]: 00:186:12:20:53
Block: 1047722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133517 RingCT/type: yes/0
Extra: 017d9acd60876973d8cb7ae8a00b3b18ed4cfbb6cae6de972e9e8c5a609eeae0ac0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ebe1891a6d9173a9d29d2bf8f6491ec312d6ec863b760f9465b1391bcd0ae11 0.600000000000 1517621 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": 1047732, "vin": [ { "gen": { "height": 1047722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ebe1891a6d9173a9d29d2bf8f6491ec312d6ec863b760f9465b1391bcd0ae11" } } ], "extra": [ 1, 125, 154, 205, 96, 135, 105, 115, 216, 203, 122, 232, 160, 11, 59, 24, 237, 76, 251, 182, 202, 230, 222, 151, 46, 158, 140, 90, 96, 158, 234, 224, 172, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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