Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fc0755440b9fb5beb831e54d92bf572c49c287ab9bee6e70eccf20d45262fea

Tx prefix hash: a10ccfc7e06f49d1ec057a5d3a2ab9f257d43171ed5474d93cedcb28a85b6056
Tx public key: 68169e5b88c05fdbdf9a780c7f0aa476a1cb18d43cf7d8fac5378060f3b78b70
Timestamp: 1582354418 Timestamp [UCT]: 2020-02-22 06:53:38 Age [y:d:h:m:s]: 04:258:00:53:21
Block: 70127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076825 RingCT/type: yes/0
Extra: 0168169e5b88c05fdbdf9a780c7f0aa476a1cb18d43cf7d8fac5378060f3b78b7002110000001fd81c26c0000000000000000000

1 output(s) for total of 359.452030633000 dcy

stealth address amount amount idx
00: 66d4f0ddae99c6e8cae6fa347b054ea59d93e5207171dda7743d9be4d31afa8a 359.452030633000 129445 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": 70137, "vin": [ { "gen": { "height": 70127 } } ], "vout": [ { "amount": 359452030633, "target": { "key": "66d4f0ddae99c6e8cae6fa347b054ea59d93e5207171dda7743d9be4d31afa8a" } } ], "extra": [ 1, 104, 22, 158, 91, 136, 192, 95, 219, 223, 154, 120, 12, 127, 10, 164, 118, 161, 203, 24, 212, 60, 247, 216, 250, 197, 55, 128, 96, 243, 183, 139, 112, 2, 17, 0, 0, 0, 31, 216, 28, 38, 192, 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