Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77c1fbdb5ef4cb2faaf350cb2f6bf930ffa86dea208ddb94b97d4ff5e8c4d9ac

Tx prefix hash: a39816dc7941e93b75b7d8496ac019365ff720f8e35334dc291b54638059615e
Tx public key: e0243a4c1f3cb8d77343b6e74e57d1fac3fe968061631222d4e81165f456a876
Timestamp: 1722262274 Timestamp [UCT]: 2024-07-29 14:11:14 Age [y:d:h:m:s]: 00:276:11:43:27
Block: 1076304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197532 RingCT/type: yes/0
Extra: 01e0243a4c1f3cb8d77343b6e74e57d1fac3fe968061631222d4e81165f456a87602110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84f7242c30f8fc2ed85537e942cfbea949ff57499f107e47dd8569b49da13b6c 0.600000000000 1548841 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": 1076314, "vin": [ { "gen": { "height": 1076304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84f7242c30f8fc2ed85537e942cfbea949ff57499f107e47dd8569b49da13b6c" } } ], "extra": [ 1, 224, 36, 58, 76, 31, 60, 184, 215, 115, 67, 182, 231, 78, 87, 209, 250, 195, 254, 150, 128, 97, 99, 18, 34, 212, 232, 17, 101, 244, 86, 168, 118, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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