Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f018a3279a2e0cf5672e21916b2ea95f52422442c17a28789de6298ee0f9bd27

Tx prefix hash: 488adf388631f75c47fe0753140bff865eadfb4923f33b9e405eafc959f136c3
Tx public key: fddf7c30a214dea37f195da3dba966b9ef39b801ebfe6a176cb1aa700e51e4b4
Timestamp: 1695996601 Timestamp [UCT]: 2023-09-29 14:10:01 Age [y:d:h:m:s]: 01:237:10:50:26
Block: 858752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430808 RingCT/type: yes/0
Extra: 01fddf7c30a214dea37f195da3dba966b9ef39b801ebfe6a176cb1aa700e51e4b4021100000006faf35c9c000000000000000000

1 output(s) for total of 0.876189779000 dcy

stealth address amount amount idx
00: f09dd768fca4f8d6f25266ec6b99f4440ab8570916a18f08a199461c2e4143fd 0.876189779000 1312944 of 0

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": 858762, "vin": [ { "gen": { "height": 858752 } } ], "vout": [ { "amount": 876189779, "target": { "key": "f09dd768fca4f8d6f25266ec6b99f4440ab8570916a18f08a199461c2e4143fd" } } ], "extra": [ 1, 253, 223, 124, 48, 162, 20, 222, 163, 127, 25, 93, 163, 219, 169, 102, 185, 239, 57, 184, 1, 235, 254, 106, 23, 108, 177, 170, 112, 14, 81, 228, 180, 2, 17, 0, 0, 0, 6, 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