Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d512ccae424ba325475e1733a61868692ce746385b6710295ea82450eeb32b05

Tx prefix hash: d980fb954893266a01326f7f0781233527b9ac383427e40764bd5f9e049a56ea
Tx public key: c69b6fc194d55950b1f0d142cb8072b8ce0aa30761d5992ce2d96c9582439b9d
Timestamp: 1731909190 Timestamp [UCT]: 2024-11-18 05:53:10 Age [y:d:h:m:s]: 00:216:00:48:12
Block: 1156194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154089 RingCT/type: yes/0
Extra: 01c69b6fc194d55950b1f0d142cb8072b8ce0aa30761d5992ce2d96c9582439b9d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 873ff58f3b23ed6374023d897e56352f826f73c1e271aeb5630834b99dac704f 0.600000000000 1641817 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": 1156204, "vin": [ { "gen": { "height": 1156194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "873ff58f3b23ed6374023d897e56352f826f73c1e271aeb5630834b99dac704f" } } ], "extra": [ 1, 198, 155, 111, 193, 148, 213, 89, 80, 177, 240, 209, 66, 203, 128, 114, 184, 206, 10, 163, 7, 97, 213, 153, 44, 226, 217, 108, 149, 130, 67, 155, 157, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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