Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44b9e62b216dd53b471bd959f40e69ca3e1252b4dbc91cfe0af352f937148f48

Tx prefix hash: b5979fd55fba9758b44ee93c8e3a0849e15087a2288074712cb9812f7d7d3f31
Tx public key: 0f769ad019c6356cc09cb6e66e39a8b573ebf54a0ec0194eb1635b48660fbd3f
Timestamp: 1733324158 Timestamp [UCT]: 2024-12-04 14:55:58 Age [y:d:h:m:s]: 00:117:08:57:23
Block: 1167914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83692 RingCT/type: yes/0
Extra: 010f769ad019c6356cc09cb6e66e39a8b573ebf54a0ec0194eb1635b48660fbd3f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0458d735e900026c0943e1fb16a2abcf5420716e9d22bab46039d0d332e9d45e 0.600000000000 1653619 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": 1167924, "vin": [ { "gen": { "height": 1167914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0458d735e900026c0943e1fb16a2abcf5420716e9d22bab46039d0d332e9d45e" } } ], "extra": [ 1, 15, 118, 154, 208, 25, 198, 53, 108, 192, 156, 182, 230, 110, 57, 168, 181, 115, 235, 245, 74, 14, 192, 25, 78, 177, 99, 91, 72, 102, 15, 189, 63, 2, 17, 0, 0, 0, 2, 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