Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42910c10562684a830f4c47fb3177d0a00776d8e4a2ed914da12506a729228f3

Tx prefix hash: c0122982bb31c6878a29480e92ddd144c7220c1cbebeab2a7064a235e93f0c58
Tx public key: c3429995c678a445d6fc0933e503052103e6d23dd5c29b0b1a135252df307b5c
Timestamp: 1718550416 Timestamp [UCT]: 2024-06-16 15:06:56 Age [y:d:h:m:s]: 00:305:02:34:57
Block: 1045550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218022 RingCT/type: yes/0
Extra: 01c3429995c678a445d6fc0933e503052103e6d23dd5c29b0b1a135252df307b5c0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eeb9e510402475b3bc0e354425957033d5cbbaa23fd6369826dc44bf125907d 0.600000000000 1515153 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": 1045560, "vin": [ { "gen": { "height": 1045550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eeb9e510402475b3bc0e354425957033d5cbbaa23fd6369826dc44bf125907d" } } ], "extra": [ 1, 195, 66, 153, 149, 198, 120, 164, 69, 214, 252, 9, 51, 229, 3, 5, 33, 3, 230, 210, 61, 213, 194, 155, 11, 26, 19, 82, 82, 223, 48, 123, 92, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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