Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c157623225b009ae327c217200c93a91b54c2b28ab3d6f11cb66670961a9408

Tx prefix hash: 1406d4d849a80543d568ee90a3c60f60724342dc49522aab057f20d3e0803f03
Tx public key: 90b238a620b7a5421307ae5f4f910d3792465adfb8bf309cb2cfa0f79abb114f
Timestamp: 1736889075 Timestamp [UCT]: 2025-01-14 21:11:15 Age [y:d:h:m:s]: 00:061:14:05:44
Block: 1197428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43810 RingCT/type: yes/0
Extra: 0190b238a620b7a5421307ae5f4f910d3792465adfb8bf309cb2cfa0f79abb114f021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3729689b7ad919c708e7cf1a46b2de2c9804148b78969c68b291ffd09dead9f5 0.600000000000 1684035 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": 1197438, "vin": [ { "gen": { "height": 1197428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3729689b7ad919c708e7cf1a46b2de2c9804148b78969c68b291ffd09dead9f5" } } ], "extra": [ 1, 144, 178, 56, 166, 32, 183, 165, 66, 19, 7, 174, 95, 79, 145, 13, 55, 146, 70, 90, 223, 184, 191, 48, 156, 178, 207, 160, 247, 154, 187, 17, 79, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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