Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6196ef90b7e8cb6402ff0882b7bfe6bc1faa73a8fd9883b4f457b4b02a837263

Tx prefix hash: 421e3840f985d2e4c682502dcf7923e6af444ef5338440451428f99103d84bb8
Tx public key: f0532a7042f8094a2416d6894d2fb5b84b3461df2ed0bd0f2c39f0f902dd0187
Timestamp: 1582926046 Timestamp [UCT]: 2020-02-28 21:40:46 Age [y:d:h:m:s]: 05:247:00:43:46
Block: 73629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1328592 RingCT/type: yes/0
Extra: 01f0532a7042f8094a2416d6894d2fb5b84b3461df2ed0bd0f2c39f0f902dd018702110000000712c4732d000000000000000000

1 output(s) for total of 350.002770137000 dcy

stealth address amount amount idx
00: c5c89434f071201d4f41dfe9b8915ff3f870f093a7a0f8f52ef32a034a2a871d 350.002770137000 135864 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": 73639, "vin": [ { "gen": { "height": 73629 } } ], "vout": [ { "amount": 350002770137, "target": { "key": "c5c89434f071201d4f41dfe9b8915ff3f870f093a7a0f8f52ef32a034a2a871d" } } ], "extra": [ 1, 240, 83, 42, 112, 66, 248, 9, 74, 36, 22, 214, 137, 77, 47, 181, 184, 75, 52, 97, 223, 46, 208, 189, 15, 44, 57, 240, 249, 2, 221, 1, 135, 2, 17, 0, 0, 0, 7, 18, 196, 115, 45, 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