Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2004d0a357e58c19973b41e005af99ab8512598b480315766254b12e27378dd1

Tx prefix hash: 91297bd3e14ed107a6f5e8b4fcc7ebe8e0a23a40f8b0a826439a0811bfbd27cf
Tx public key: 267312a0a51c7fc13245c4aaf56cf396e61619b1ed52d0b0d1a16adbbad0a06d
Timestamp: 1729609658 Timestamp [UCT]: 2024-10-22 15:07:38 Age [y:d:h:m:s]: 00:226:10:42:22
Block: 1137188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161685 RingCT/type: yes/0
Extra: 01267312a0a51c7fc13245c4aaf56cf396e61619b1ed52d0b0d1a16adbbad0a06d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66f3f9527e1b8b05886f39e4c0efc855e36f80d9fc448bfee6c99a7449ae354a 0.600000000000 1620633 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": 1137198, "vin": [ { "gen": { "height": 1137188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66f3f9527e1b8b05886f39e4c0efc855e36f80d9fc448bfee6c99a7449ae354a" } } ], "extra": [ 1, 38, 115, 18, 160, 165, 28, 127, 193, 50, 69, 196, 170, 245, 108, 243, 150, 230, 22, 25, 177, 237, 82, 208, 176, 209, 161, 106, 219, 186, 208, 160, 109, 2, 17, 0, 0, 0, 5, 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