Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82d2bca22274d243c590a0fa01df9273f3839a40295017e0585ab8a45d7f533e

Tx prefix hash: 60ec3fa18f429ba5ad664f78398039a5be033804e633e31a5a12c15be0b46142
Tx public key: ea0fba7d77066e7cf335090e68ae53dbc03602c0990740a35e98ea2d37a8e0b1
Timestamp: 1736347524 Timestamp [UCT]: 2025-01-08 14:45:24 Age [y:d:h:m:s]: 00:341:21:01:17
Block: 1192941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241896 RingCT/type: yes/0
Extra: 01ea0fba7d77066e7cf335090e68ae53dbc03602c0990740a35e98ea2d37a8e0b102110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d9194e8995fec36cb56dff771695ef78da14c4fd0a14d4d4e619483be022b87 0.600000000000 1679498 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": 1192951, "vin": [ { "gen": { "height": 1192941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d9194e8995fec36cb56dff771695ef78da14c4fd0a14d4d4e619483be022b87" } } ], "extra": [ 1, 234, 15, 186, 125, 119, 6, 110, 124, 243, 53, 9, 14, 104, 174, 83, 219, 192, 54, 2, 192, 153, 7, 64, 163, 94, 152, 234, 45, 55, 168, 224, 177, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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