Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b55cab40019fd7cbd285097a5ebcf0124bb37cb050ea870813da4414097a9ebe

Tx prefix hash: d79154c49ab48f59768279a88dad4285fb4525b920280a2d4f21a7f2f4cb65af
Tx public key: abbdb3b64ff313f2e296575ab9d563962ee688cc4f474e633c941b1a6c5161eb
Timestamp: 1706593886 Timestamp [UCT]: 2024-01-30 05:51:26 Age [y:d:h:m:s]: 01:068:13:27:23
Block: 946390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310071 RingCT/type: yes/0
Extra: 01abbdb3b64ff313f2e296575ab9d563962ee688cc4f474e633c941b1a6c5161eb0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d847b89d7c8f0ab74d3f952c9f69e1be8bbdac4dd4043d3d532186e7d1092bc3 0.600000000000 1404722 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": 946400, "vin": [ { "gen": { "height": 946390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d847b89d7c8f0ab74d3f952c9f69e1be8bbdac4dd4043d3d532186e7d1092bc3" } } ], "extra": [ 1, 171, 189, 179, 182, 79, 243, 19, 242, 226, 150, 87, 90, 185, 213, 99, 150, 46, 230, 136, 204, 79, 71, 78, 99, 60, 148, 27, 26, 108, 81, 97, 235, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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