Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b25aefa28b6036f1645af8213cc751cd912f0645d3dbf872d30a35c52913c8ae

Tx prefix hash: 4e87462d8ded2a60c35319bfbaf8fb5645fe177f210695218d278d45dd2702d3
Tx public key: 75798df02b8027e9287f459c3557a64264c5f9e5feab41cc9cc4d05f96876bae
Timestamp: 1722267094 Timestamp [UCT]: 2024-07-29 15:31:34 Age [y:d:h:m:s]: 00:239:17:14:23
Block: 1076347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171218 RingCT/type: yes/0
Extra: 0175798df02b8027e9287f459c3557a64264c5f9e5feab41cc9cc4d05f96876bae02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8141bb59bcb30637a27b7c1ae3fc7cdac7f5dadc6113e4f1d83fb12a98b153b4 0.600000000000 1548884 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": 1076357, "vin": [ { "gen": { "height": 1076347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8141bb59bcb30637a27b7c1ae3fc7cdac7f5dadc6113e4f1d83fb12a98b153b4" } } ], "extra": [ 1, 117, 121, 141, 240, 43, 128, 39, 233, 40, 127, 69, 156, 53, 87, 166, 66, 100, 197, 249, 229, 254, 171, 65, 204, 156, 196, 208, 95, 150, 135, 107, 174, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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