Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 745e11d6a31365d87b9cde06f70fb1b10cc762937f93692610a129af8d8cef49

Tx prefix hash: bfb2ae4aabef87c187231f7c1f01b80f0ae02c54f10b98abad3ca1c6abbf7f8d
Tx public key: e463f1c2d85c55a3574134cae602ab1ce46c9712de1e7860ff857e6f3831f8c0
Timestamp: 1697770969 Timestamp [UCT]: 2023-10-20 03:02:49 Age [y:d:h:m:s]: 01:168:14:14:46
Block: 873470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381513 RingCT/type: yes/0
Extra: 01e463f1c2d85c55a3574134cae602ab1ce46c9712de1e7860ff857e6f3831f8c002110000000833af99f4000000000000000000

1 output(s) for total of 0.783125413000 dcy

stealth address amount amount idx
00: 9a3f2d74700ca7da96797c3c7e093c1d51fce1114a241507cd426b5c0425a7d2 0.783125413000 1328620 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": 873480, "vin": [ { "gen": { "height": 873470 } } ], "vout": [ { "amount": 783125413, "target": { "key": "9a3f2d74700ca7da96797c3c7e093c1d51fce1114a241507cd426b5c0425a7d2" } } ], "extra": [ 1, 228, 99, 241, 194, 216, 92, 85, 163, 87, 65, 52, 202, 230, 2, 171, 28, 228, 108, 151, 18, 222, 30, 120, 96, 255, 133, 126, 111, 56, 49, 248, 192, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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