Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb0d9ccb594496bb3290e6ff090e87b8e4b960043838f87e3ef306a59d7c67e0

Tx prefix hash: e1be2091db1eb7a2445b9bf048b790327cc400f479f6219668b6efa64ce17e79
Tx public key: 34ad12f93c1ebc9dfb044fb81f222dfb9bd700962a5d266bf99b96dc094d6531
Timestamp: 1734822031 Timestamp [UCT]: 2024-12-21 23:00:31 Age [y:d:h:m:s]: 01:040:19:55:56
Block: 1180352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287446 RingCT/type: yes/0
Extra: 0134ad12f93c1ebc9dfb044fb81f222dfb9bd700962a5d266bf99b96dc094d6531021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26656b2dbb62edbf6df862ff057895e04820fc4f6140c4e6049e18562a84319d 0.600000000000 1666763 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": 1180362, "vin": [ { "gen": { "height": 1180352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26656b2dbb62edbf6df862ff057895e04820fc4f6140c4e6049e18562a84319d" } } ], "extra": [ 1, 52, 173, 18, 249, 60, 30, 188, 157, 251, 4, 79, 184, 31, 34, 45, 251, 155, 215, 0, 150, 42, 93, 38, 107, 249, 155, 150, 220, 9, 77, 101, 49, 2, 17, 0, 0, 0, 1, 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