Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8edb69671bf15cae2d1ed76b58615877fe5fa3abb2e387fa262d2f4df4ced97c

Tx prefix hash: 63357a413232a81b46d77ac1d9816a482edb0576f0c8fb682be378a1408c9d70
Tx public key: a169044d88f275a6956ecfa949d3c300f89cc8d9b7e5e0087a2d7dc4d8313ea7
Timestamp: 1730892906 Timestamp [UCT]: 2024-11-06 11:35:06 Age [y:d:h:m:s]: 00:202:07:29:30
Block: 1147773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144461 RingCT/type: yes/0
Extra: 01a169044d88f275a6956ecfa949d3c300f89cc8d9b7e5e0087a2d7dc4d8313ea7021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7777406dd95a87396382f79803ec061fbdfa71b6083b93fbe5bcd4d7fb686186 0.600000000000 1632474 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": 1147783, "vin": [ { "gen": { "height": 1147773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7777406dd95a87396382f79803ec061fbdfa71b6083b93fbe5bcd4d7fb686186" } } ], "extra": [ 1, 161, 105, 4, 77, 136, 242, 117, 166, 149, 110, 207, 169, 73, 211, 195, 0, 248, 156, 200, 217, 183, 229, 224, 8, 122, 45, 125, 196, 216, 49, 62, 167, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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