Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93ca32b595330cbfd31220b592f8e2ed4d815cebb8760f3307dc7ba80a2b671e

Tx prefix hash: 5c6408dfd51929e29a8e48b22be659625baf42a556d6ce620c495deb60efb6fc
Tx public key: 069309b499f21f4c6f2c226a1d07a15e6f6c49df0d433bf63405e19c0eed57a9
Timestamp: 1583236375 Timestamp [UCT]: 2020-03-03 11:52:55 Age [y:d:h:m:s]: 05:090:23:55:53
Block: 75418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1220187 RingCT/type: yes/0
Extra: 01069309b499f21f4c6f2c226a1d07a15e6f6c49df0d433bf63405e19c0eed57a90211000001610aca7173000000000000000000

1 output(s) for total of 345.230895797000 dcy

stealth address amount amount idx
00: 1292b0df9c38e012880eb5c03e99b714d6df315d79d5f45c8498670322943ed5 345.230895797000 139357 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": 75428, "vin": [ { "gen": { "height": 75418 } } ], "vout": [ { "amount": 345230895797, "target": { "key": "1292b0df9c38e012880eb5c03e99b714d6df315d79d5f45c8498670322943ed5" } } ], "extra": [ 1, 6, 147, 9, 180, 153, 242, 31, 76, 111, 44, 34, 106, 29, 7, 161, 94, 111, 108, 73, 223, 13, 67, 59, 246, 52, 5, 225, 156, 14, 237, 87, 169, 2, 17, 0, 0, 1, 97, 10, 202, 113, 115, 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