Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc12221b5031799cfab423c68fa1f7723bdcaffb5cd358d81f0abf08d702b6a4

Tx prefix hash: 382a267b0ecd2d8db636a6b206aafb0bc2a0a36e45507ca0231e7921a22bd79f
Tx public key: 8e555055cb16fbe8abd06e13609bfa026deb9e87b6a283a426fa83afa22237c1
Timestamp: 1700676471 Timestamp [UCT]: 2023-11-22 18:07:51 Age [y:d:h:m:s]: 01:058:17:19:57
Block: 897354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303325 RingCT/type: yes/0
Extra: 018e555055cb16fbe8abd06e13609bfa026deb9e87b6a283a426fa83afa22237c102110000000475e3f0e9000000000000000000

1 output(s) for total of 0.652670038000 dcy

stealth address amount amount idx
00: 4726ab7c9a1215c1fdb0bbe9c49be2822d2dcbfa7eac6ba9f2104979072cac6e 0.652670038000 1353729 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": 897364, "vin": [ { "gen": { "height": 897354 } } ], "vout": [ { "amount": 652670038, "target": { "key": "4726ab7c9a1215c1fdb0bbe9c49be2822d2dcbfa7eac6ba9f2104979072cac6e" } } ], "extra": [ 1, 142, 85, 80, 85, 203, 22, 251, 232, 171, 208, 110, 19, 96, 155, 250, 2, 109, 235, 158, 135, 182, 162, 131, 164, 38, 250, 131, 175, 162, 34, 55, 193, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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