Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7373fada389cc79798cec40d5e17235b5880ad7cc56fa1f06c787ba375b10f7

Tx prefix hash: dec894fc004f1cb4b8d3c5164e2e92f749689b6c3342f9267443a9e8c3d76f1d
Tx public key: 71b730239e04ca238c596460b6ab2ab411ad6e404a41f7f106a7a4395319a9ac
Timestamp: 1710380063 Timestamp [UCT]: 2024-03-14 01:34:23 Age [y:d:h:m:s]: 01:091:06:56:25
Block: 977820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326212 RingCT/type: yes/0
Extra: 0171b730239e04ca238c596460b6ab2ab411ad6e404a41f7f106a7a4395319a9ac021100000001a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3eeee13e74e612a53081c8b92747fa514d0ace2fc3c7e8eb944b591a3739d46 0.600000000000 1437827 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": 977830, "vin": [ { "gen": { "height": 977820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3eeee13e74e612a53081c8b92747fa514d0ace2fc3c7e8eb944b591a3739d46" } } ], "extra": [ 1, 113, 183, 48, 35, 158, 4, 202, 35, 140, 89, 100, 96, 182, 171, 42, 180, 17, 173, 110, 64, 74, 65, 247, 241, 6, 167, 164, 57, 83, 25, 169, 172, 2, 17, 0, 0, 0, 1, 165, 223, 157, 134, 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