Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea9372ad37cb7f91ab1b6cc3dfee7689e0eb677f24110d30f77919fbab33466c

Tx prefix hash: e893fce8a31a238d1f1d0434b22a9f3b6fa836a014ab71be18aa3e70336e305a
Tx public key: 51d18430181ed4ef71e3fa8448683754acd7cb616c8004e5ff2e0a8fa1ce31e3
Timestamp: 1730131020 Timestamp [UCT]: 2024-10-28 15:57:00 Age [y:d:h:m:s]: 00:085:20:59:32
Block: 1141478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61388 RingCT/type: yes/0
Extra: 0151d18430181ed4ef71e3fa8448683754acd7cb616c8004e5ff2e0a8fa1ce31e302110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88ead754f330d4bceb49df36d5e990a53c027414378db7d1c94ad40e96b6e963 0.600000000000 1625285 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": 1141488, "vin": [ { "gen": { "height": 1141478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88ead754f330d4bceb49df36d5e990a53c027414378db7d1c94ad40e96b6e963" } } ], "extra": [ 1, 81, 209, 132, 48, 24, 30, 212, 239, 113, 227, 250, 132, 72, 104, 55, 84, 172, 215, 203, 97, 108, 128, 4, 229, 255, 46, 10, 143, 161, 206, 49, 227, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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