Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e1671fac0c6b7cb58bb683d6375a3e439014ec841cdc049c58a2965c251491f

Tx prefix hash: d844ad554fdd7d345601856f9b1d3bf72b439966067f746a285313295d0dc9d8
Tx public key: 6d1e742bef33a720c9967659f04b8b1e99ea2c2f1a6bcd6c036b0f710b26a689
Timestamp: 1584904980 Timestamp [UCT]: 2020-03-22 19:23:00 Age [y:d:h:m:s]: 04:290:07:47:12
Block: 86603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104573 RingCT/type: yes/0
Extra: 016d1e742bef33a720c9967659f04b8b1e99ea2c2f1a6bcd6c036b0f710b26a689021100000363c2c2f844000000000000000000

1 output(s) for total of 316.998055667000 dcy

stealth address amount amount idx
00: 145a2172ac7ab6385db1305a097463608db75b28a6b8ad22a8c5011e64ec3daa 316.998055667000 156263 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": 86613, "vin": [ { "gen": { "height": 86603 } } ], "vout": [ { "amount": 316998055667, "target": { "key": "145a2172ac7ab6385db1305a097463608db75b28a6b8ad22a8c5011e64ec3daa" } } ], "extra": [ 1, 109, 30, 116, 43, 239, 51, 167, 32, 201, 150, 118, 89, 240, 75, 139, 30, 153, 234, 44, 47, 26, 107, 205, 108, 3, 107, 15, 113, 11, 38, 166, 137, 2, 17, 0, 0, 3, 99, 194, 194, 248, 68, 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