Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7bee5cf6dc2471263965a661a3e803491b6d144b71e44e1868180d42e77c190

Tx prefix hash: 3fd1eed7bac3acc14d36f99286189ff6330cfeee34a6237f286faf67a381ded5
Tx public key: 1994ca964084e9c83d9a2669dc03c3dd85e6ecba1f1f3a9597fd5cb09224be81
Timestamp: 1577457774 Timestamp [UCT]: 2019-12-27 14:42:54 Age [y:d:h:m:s]: 05:114:20:13:49
Block: 32911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1231887 RingCT/type: yes/0
Extra: 011994ca964084e9c83d9a2669dc03c3dd85e6ecba1f1f3a9597fd5cb09224be81021100000003d81c26c0000000000000000000

1 output(s) for total of 477.485895805000 dcy

stealth address amount amount idx
00: 7f2dce3ef3b1706b9c17c5a11cf3c1ccc50ab1270a99c43a6b2dc76adad9e42a 477.485895805000 54853 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": 32921, "vin": [ { "gen": { "height": 32911 } } ], "vout": [ { "amount": 477485895805, "target": { "key": "7f2dce3ef3b1706b9c17c5a11cf3c1ccc50ab1270a99c43a6b2dc76adad9e42a" } } ], "extra": [ 1, 25, 148, 202, 150, 64, 132, 233, 200, 61, 154, 38, 105, 220, 3, 195, 221, 133, 230, 236, 186, 31, 31, 58, 149, 151, 253, 92, 176, 146, 36, 190, 129, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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