Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71737feb15e5846e42feecd5efc4872040754ae6c619437fcdeef65825935f8a

Tx prefix hash: d36bc2fe5302b721904b8e2d5dbc242ae93ebc3820c770d5f9ccf94c7667628a
Tx public key: 0478c4ef916e16731480af9a06df07a8b77063083b4a1036150ac3af6ab5eae6
Timestamp: 1737342373 Timestamp [UCT]: 2025-01-20 03:06:13 Age [y:d:h:m:s]: 00:149:14:09:44
Block: 1201134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106659 RingCT/type: yes/0
Extra: 010478c4ef916e16731480af9a06df07a8b77063083b4a1036150ac3af6ab5eae60211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0dab6f22a586b6e481a3a4c3605d5ec18eac9738917c1e34efc092a413b4d2f 0.600000000000 1687783 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": 1201144, "vin": [ { "gen": { "height": 1201134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0dab6f22a586b6e481a3a4c3605d5ec18eac9738917c1e34efc092a413b4d2f" } } ], "extra": [ 1, 4, 120, 196, 239, 145, 110, 22, 115, 20, 128, 175, 154, 6, 223, 7, 168, 183, 112, 99, 8, 59, 74, 16, 54, 21, 10, 195, 175, 106, 181, 234, 230, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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