Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85baa9da463a1b19d16462df213c4be5e9f220f16c03b17e079be6cc9dd9bfcf

Tx prefix hash: 5924ac2cd8267f80ce74325af5c45baffc8ee5cb24754f1cc98aebd922c3c854
Tx public key: e8c8deb0beb94118cc3b6d8a3ec1460e8d887d6655903807ae276aa1191e8927
Timestamp: 1750793353 Timestamp [UCT]: 2025-06-24 19:29:13 Age [y:d:h:m:s]: 00:145:02:45:01
Block: 1312017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101652 RingCT/type: yes/0
Extra: 01e8c8deb0beb94118cc3b6d8a3ec1460e8d887d6655903807ae276aa1191e8927021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c8bffc1ca980c4dfedf427e6d7345916f49d62b39b0f873690130097e9e1985 0.600000000000 1799648 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": 1312027, "vin": [ { "gen": { "height": 1312017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c8bffc1ca980c4dfedf427e6d7345916f49d62b39b0f873690130097e9e1985" } } ], "extra": [ 1, 232, 200, 222, 176, 190, 185, 65, 24, 204, 59, 109, 138, 62, 193, 70, 14, 141, 136, 125, 102, 85, 144, 56, 7, 174, 39, 106, 161, 25, 30, 137, 39, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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