Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4377a6e031b1b270f65e5529860826925368060c26ec79252d0e051cb04b1b92

Tx prefix hash: e3ca17ec617d2f27c1ae041816673fa84991309f291dc14c0895d778da8d521f
Tx public key: 6659e920a632bdb7f294e814fa01fff1881a62c1c08164ee397a81b4cfd66eab
Timestamp: 1577973928 Timestamp [UCT]: 2020-01-02 14:05:28 Age [y:d:h:m:s]: 05:072:05:27:22
Block: 37259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201362 RingCT/type: yes/0
Extra: 016659e920a632bdb7f294e814fa01fff1881a62c1c08164ee397a81b4cfd66eab02110000000e8a2ee0d9000000000000000000

1 output(s) for total of 461.898250926000 dcy

stealth address amount amount idx
00: bcc4c713a36f39330301dd84e4f0175e7bd927376ed64f5822515398c60ed84d 461.898250926000 63183 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": 37269, "vin": [ { "gen": { "height": 37259 } } ], "vout": [ { "amount": 461898250926, "target": { "key": "bcc4c713a36f39330301dd84e4f0175e7bd927376ed64f5822515398c60ed84d" } } ], "extra": [ 1, 102, 89, 233, 32, 166, 50, 189, 183, 242, 148, 232, 20, 250, 1, 255, 241, 136, 26, 98, 193, 192, 129, 100, 238, 57, 122, 129, 180, 207, 214, 110, 171, 2, 17, 0, 0, 0, 14, 138, 46, 224, 217, 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