Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2741b5c8f2608b12597f1723209c93f6ce590e0bf1a3d032d86de095c5e1af4

Tx prefix hash: 47e98e1e05384a461701ed40af77431d16ba884897623319c9d86bfa7a4c20c5
Tx public key: 82446a14c1a2fc8675fd7e9a81078788511f632043591a7ac09fc9ffa1026a37
Timestamp: 1697514248 Timestamp [UCT]: 2023-10-17 03:44:08 Age [y:d:h:m:s]: 01:095:07:57:32
Block: 871333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329350 RingCT/type: yes/0
Extra: 0182446a14c1a2fc8675fd7e9a81078788511f632043591a7ac09fc9ffa1026a37021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.795998206000 dcy

stealth address amount amount idx
00: f49091d38fba938c6dc7f191c491d4a9aa899e94258a260a582af28cee33f5e4 0.795998206000 1326314 of 0

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": 871343, "vin": [ { "gen": { "height": 871333 } } ], "vout": [ { "amount": 795998206, "target": { "key": "f49091d38fba938c6dc7f191c491d4a9aa899e94258a260a582af28cee33f5e4" } } ], "extra": [ 1, 130, 68, 106, 20, 193, 162, 252, 134, 117, 253, 126, 154, 129, 7, 135, 136, 81, 31, 99, 32, 67, 89, 26, 122, 192, 159, 201, 255, 161, 2, 106, 55, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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