Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3646a3f7e38c58c188b2dfd884ab34248108f35f1d3bfbfdc4390e16fee3d4d

Tx prefix hash: c853fafc1e5df28ad90a599a5acaac349f71e14fa1a023e775838431a8cdb19d
Tx public key: fd5d08667043cfdb1433769d1f6060b6480ebedf7231850da022d0ff89608bcc
Timestamp: 1696947234 Timestamp [UCT]: 2023-10-10 14:13:54 Age [y:d:h:m:s]: 01:083:10:50:11
Block: 866648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320881 RingCT/type: yes/0
Extra: 01fd5d08667043cfdb1433769d1f6060b6480ebedf7231850da022d0ff89608bcc021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.824964852000 dcy

stealth address amount amount idx
00: a14af0ec64ec7b64eb367b5a79f07893bb68b9701b087b8ec8812a1878f1b721 0.824964852000 1321268 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": 866658, "vin": [ { "gen": { "height": 866648 } } ], "vout": [ { "amount": 824964852, "target": { "key": "a14af0ec64ec7b64eb367b5a79f07893bb68b9701b087b8ec8812a1878f1b721" } } ], "extra": [ 1, 253, 93, 8, 102, 112, 67, 207, 219, 20, 51, 118, 157, 31, 96, 96, 182, 72, 14, 190, 223, 114, 49, 133, 13, 160, 34, 208, 255, 137, 96, 139, 204, 2, 17, 0, 0, 0, 3, 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