Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9bd998cac158b44a42487c95f60d930b624a8cd2954bf2ce278d2375dd2f2eb

Tx prefix hash: 73d12b5ac528c1665a63faa96bd4782e10cd47e46844ef9d4838fdf3ae0465d7
Tx public key: 21c20b9f3fcf7b8e9d09edbdf313593c8fc3389e8870b3edfc0044850fa0191a
Timestamp: 1703669248 Timestamp [UCT]: 2023-12-27 09:27:28 Age [y:d:h:m:s]: 01:321:03:14:40
Block: 922169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488353 RingCT/type: yes/0
Extra: 0121c20b9f3fcf7b8e9d09edbdf313593c8fc3389e8870b3edfc0044850fa0191a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 250625aa3cf337c21e1df1c4459ef847fc7a4dfd2e57993224feebb3171d862a 0.600000000000 1379863 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": 922179, "vin": [ { "gen": { "height": 922169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "250625aa3cf337c21e1df1c4459ef847fc7a4dfd2e57993224feebb3171d862a" } } ], "extra": [ 1, 33, 194, 11, 159, 63, 207, 123, 142, 157, 9, 237, 189, 243, 19, 89, 60, 143, 195, 56, 158, 136, 112, 179, 237, 252, 0, 68, 133, 15, 160, 25, 26, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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