Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6dc59113835b658297635f52d25df5249015236ca71a8e6dd6f0f17608a086c

Tx prefix hash: eb000af3c77b5e99ed9290ee081ae7158a73813854aa90ea84e4b31cde7cf8e8
Tx public key: 7d3306bcb2438b1477312b45c90284cdcbdc35bd11001dcc9e8a36ef826ab93d
Timestamp: 1659767674 Timestamp [UCT]: 2022-08-06 06:34:34 Age [y:d:h:m:s]: 02:254:21:34:19
Block: 559783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 703385 RingCT/type: yes/0
Extra: 017d3306bcb2438b1477312b45c90284cdcbdc35bd11001dcc9e8a36ef826ab93d02110000000c6570b1ef000000000000000000

1 output(s) for total of 8.574457695000 dcy

stealth address amount amount idx
00: 861838dc13ec9091422e5a9af3b724eb1cdece33f0f8e20d7b040b2dd80208a1 8.574457695000 991961 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": 559793, "vin": [ { "gen": { "height": 559783 } } ], "vout": [ { "amount": 8574457695, "target": { "key": "861838dc13ec9091422e5a9af3b724eb1cdece33f0f8e20d7b040b2dd80208a1" } } ], "extra": [ 1, 125, 51, 6, 188, 178, 67, 139, 20, 119, 49, 43, 69, 201, 2, 132, 205, 203, 220, 53, 189, 17, 0, 29, 204, 158, 138, 54, 239, 130, 106, 185, 61, 2, 17, 0, 0, 0, 12, 101, 112, 177, 239, 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