Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 225c848d630be1e7017197c4c108c3a9ce6dbfeec9a923afd9e959f08c7b09ca

Tx prefix hash: 5bfb9feee81b488934bccbb39c4469c594bd5e22272d3c806ad3aff3a9e95b87
Tx public key: 91c9e02342750df7b09077b9c0b343f34e38af00236ede56c0f31a6e72bac9bf
Timestamp: 1709059370 Timestamp [UCT]: 2024-02-27 18:42:50 Age [y:d:h:m:s]: 00:260:14:07:22
Block: 966859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186556 RingCT/type: yes/0
Extra: 0191c9e02342750df7b09077b9c0b343f34e38af00236ede56c0f31a6e72bac9bf0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6444ce45ebbd8cbcbf0d3c1feed3e1249ad61522c192f6c3d5288ce09c9fb9b 0.600000000000 1426630 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": 966869, "vin": [ { "gen": { "height": 966859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6444ce45ebbd8cbcbf0d3c1feed3e1249ad61522c192f6c3d5288ce09c9fb9b" } } ], "extra": [ 1, 145, 201, 224, 35, 66, 117, 13, 247, 176, 144, 119, 185, 192, 179, 67, 243, 78, 56, 175, 0, 35, 110, 222, 86, 192, 243, 26, 110, 114, 186, 201, 191, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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