Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85f8991b01ca60197693743b9c2d83a3bb4fb862309fbb16f21081925fa1ae05

Tx prefix hash: 2efdf1c42a5f96c9082b504bc6222d1e373b72813c8048e8031f57f108b24b40
Tx public key: d972af3096f045c7841a5cf8690ce3dd9c9cb12532791405a2c059530d4f159c
Timestamp: 1731538237 Timestamp [UCT]: 2024-11-13 22:50:37 Age [y:d:h:m:s]: 00:154:03:58:06
Block: 1153128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110000 RingCT/type: yes/0
Extra: 01d972af3096f045c7841a5cf8690ce3dd9c9cb12532791405a2c059530d4f159c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 917c16b0616aa06fd46999308851275019dfe992581f3cdcbc8a875870b1d26a 0.600000000000 1638735 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": 1153138, "vin": [ { "gen": { "height": 1153128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "917c16b0616aa06fd46999308851275019dfe992581f3cdcbc8a875870b1d26a" } } ], "extra": [ 1, 217, 114, 175, 48, 150, 240, 69, 199, 132, 26, 92, 248, 105, 12, 227, 221, 156, 156, 177, 37, 50, 121, 20, 5, 162, 192, 89, 83, 13, 79, 21, 156, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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