Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeaad0d4ed9d13ba3e3dd0072586492f3f0249357fbb32f4129f813c5a78dda6

Tx prefix hash: ed16732c4d117b2bde4ffb9c14a180cbe161a3906346886a50487a6095cefd44
Tx public key: fb368dce392cf9a6b27c4203e7a506222abcc17f3cfc5d9174f9b6b13bbe171a
Timestamp: 1702533527 Timestamp [UCT]: 2023-12-14 05:58:47 Age [y:d:h:m:s]: 01:113:14:19:06
Block: 912745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342321 RingCT/type: yes/0
Extra: 01fb368dce392cf9a6b27c4203e7a506222abcc17f3cfc5d9174f9b6b13bbe171a021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 209bbd45c69db80c0bfa0fb22d7f065020bb49e5aa3ce51f59c02fd1c28765c6 0.600000000000 1369981 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": 912755, "vin": [ { "gen": { "height": 912745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "209bbd45c69db80c0bfa0fb22d7f065020bb49e5aa3ce51f59c02fd1c28765c6" } } ], "extra": [ 1, 251, 54, 141, 206, 57, 44, 249, 166, 178, 124, 66, 3, 231, 165, 6, 34, 42, 188, 193, 127, 60, 252, 93, 145, 116, 249, 182, 177, 59, 190, 23, 26, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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