Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dad8c32bf3a96a84f3f1e8a48793e32b89a915b617acc04ea14785a8a96845b1

Tx prefix hash: 8ca02ec80e80f954c4e2184cfab512e2ef4c771bd4d6ba392ee8ced8e0696078
Tx public key: 43dcf6675506ae31b2cdf4613863c2926a9d79bede8af1c590f6653b6d29bfec
Timestamp: 1722026667 Timestamp [UCT]: 2024-07-26 20:44:27 Age [y:d:h:m:s]: 00:171:21:30:24
Block: 1074346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122994 RingCT/type: yes/0
Extra: 0143dcf6675506ae31b2cdf4613863c2926a9d79bede8af1c590f6653b6d29bfec021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88a76c53fde4d0b40eb811d16103ca47e61bc2df78b3db4df9bb4635cda13926 0.600000000000 1546859 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": 1074356, "vin": [ { "gen": { "height": 1074346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88a76c53fde4d0b40eb811d16103ca47e61bc2df78b3db4df9bb4635cda13926" } } ], "extra": [ 1, 67, 220, 246, 103, 85, 6, 174, 49, 178, 205, 244, 97, 56, 99, 194, 146, 106, 157, 121, 190, 222, 138, 241, 197, 144, 246, 101, 59, 109, 41, 191, 236, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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