Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32677db4e7e9a57a00252beb8ef48f4b39aae3770727624a584703c3967a123a

Tx prefix hash: add191acdb4bc78888903549858e88e06b862e0a9bbcf61620c1630b78c1e860
Tx public key: 814a6e1d6f4bfd3112cd0a467cd71cd9ccce52d5fbf22cfdbeb4c422b93d804c
Timestamp: 1705498127 Timestamp [UCT]: 2024-01-17 13:28:47 Age [y:d:h:m:s]: 01:064:10:19:54
Block: 937309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307140 RingCT/type: yes/0
Extra: 01814a6e1d6f4bfd3112cd0a467cd71cd9ccce52d5fbf22cfdbeb4c422b93d804c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e1db0ab11a84bc83844538e9d83c731d39238c8da9e2c87c71cd197bae81c25 0.600000000000 1395359 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": 937319, "vin": [ { "gen": { "height": 937309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e1db0ab11a84bc83844538e9d83c731d39238c8da9e2c87c71cd197bae81c25" } } ], "extra": [ 1, 129, 74, 110, 29, 111, 75, 253, 49, 18, 205, 10, 70, 124, 215, 28, 217, 204, 206, 82, 213, 251, 242, 44, 253, 190, 180, 196, 34, 185, 61, 128, 76, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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