Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb5ffae26cd8905ca744df4c3d6e8c315362ac24476ef1d18a1e08d04ce85ec1

Tx prefix hash: d0fd1f75e26e7c2dfdd173a06ef9947f8e8174e7e6bd3395945e3fd4edcbec75
Tx public key: 6f3b652b8bc74f023401b7fb9d3998efae41c18b5555f675c83b0fded168f0f5
Timestamp: 1723164141 Timestamp [UCT]: 2024-08-09 00:42:21 Age [y:d:h:m:s]: 00:075:05:47:54
Block: 1083778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53874 RingCT/type: yes/0
Extra: 016f3b652b8bc74f023401b7fb9d3998efae41c18b5555f675c83b0fded168f0f502110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c422a44fc1e8a4f034d0a9fee67d96bf450be15fee1ec74615dc992b4042bb17 0.600000000000 1557821 of 15

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": 1083788, "vin": [ { "gen": { "height": 1083778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c422a44fc1e8a4f034d0a9fee67d96bf450be15fee1ec74615dc992b4042bb17" } } ], "extra": [ 1, 111, 59, 101, 43, 139, 199, 79, 2, 52, 1, 183, 251, 157, 57, 152, 239, 174, 65, 193, 139, 85, 85, 246, 117, 200, 59, 15, 222, 209, 104, 240, 245, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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