Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98f3ca2cc0f1e3cb4c5d6cbdc6184772848342b3b21a5a434319af6512283f09

Tx prefix hash: a20965f3884fb9d1a82de169fbd6a258e40d0dec7a3a0f8891fb2e1cc61f7477
Tx public key: e067ed3d388fa40c8776f814165ac058d03acea4309915f80d49ee814d58be96
Timestamp: 1649459880 Timestamp [UCT]: 2022-04-08 23:18:00 Age [y:d:h:m:s]: 02:237:12:13:41
Block: 476159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 689516 RingCT/type: yes/0
Extra: 01e067ed3d388fa40c8776f814165ac058d03acea4309915f80d49ee814d58be96021100000002cb8520c2000000000000000000

1 output(s) for total of 16.229592401000 dcy

stealth address amount amount idx
00: c2c85c30b167fc3c2734ebd15d95dc2c6977095849f507129a89e070c5cd9ffb 16.229592401000 896552 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": 476169, "vin": [ { "gen": { "height": 476159 } } ], "vout": [ { "amount": 16229592401, "target": { "key": "c2c85c30b167fc3c2734ebd15d95dc2c6977095849f507129a89e070c5cd9ffb" } } ], "extra": [ 1, 224, 103, 237, 61, 56, 143, 164, 12, 135, 118, 248, 20, 22, 90, 192, 88, 208, 58, 206, 164, 48, 153, 21, 248, 13, 73, 238, 129, 77, 88, 190, 150, 2, 17, 0, 0, 0, 2, 203, 133, 32, 194, 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