Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9356817fa5bb0723800727f75e4e76c2e76c52de1419d1ce2c4038980609496d

Tx prefix hash: 26fa3e4e9af70c4835efa6a74d26ab1f1fdd3e6833033cbbf61a69bfd15caf10
Tx public key: f2233ce9ddcb94226aa0d8b091b0b3a59fcdb30fc8d1389666d3fa3dbe02dd1a
Timestamp: 1583753653 Timestamp [UCT]: 2020-03-09 11:34:13 Age [y:d:h:m:s]: 04:261:22:11:49
Block: 79458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1081864 RingCT/type: yes/0
Extra: 01f2233ce9ddcb94226aa0d8b091b0b3a59fcdb30fc8d1389666d3fa3dbe02dd1a0211000000396d997e00000000000000000000

1 output(s) for total of 334.752209456000 dcy

stealth address amount amount idx
00: 345df9d7b197878ecd71fa6a81722b4995c34c5a26f51279b7498a1f55820bfb 334.752209456000 145308 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": 79468, "vin": [ { "gen": { "height": 79458 } } ], "vout": [ { "amount": 334752209456, "target": { "key": "345df9d7b197878ecd71fa6a81722b4995c34c5a26f51279b7498a1f55820bfb" } } ], "extra": [ 1, 242, 35, 60, 233, 221, 203, 148, 34, 106, 160, 216, 176, 145, 176, 179, 165, 159, 205, 179, 15, 200, 209, 56, 150, 102, 211, 250, 61, 190, 2, 221, 26, 2, 17, 0, 0, 0, 57, 109, 153, 126, 0, 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