Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17c595ae9bba463db28cdc7d7f2d214c74acc3e131df136a4e833bd156d3bcaf

Tx prefix hash: 005e5cf67b42c85e022e62dca34d37fa0893664006b5cb84fd68bb8bc39dc761
Tx public key: 19e26702b547c51d50b1f2d0e052ea802f1fa07b3f7aa2421968c6f10d342d3f
Timestamp: 1706492593 Timestamp [UCT]: 2024-01-29 01:43:13 Age [y:d:h:m:s]: 01:026:05:09:34
Block: 945539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279780 RingCT/type: yes/0
Extra: 0119e26702b547c51d50b1f2d0e052ea802f1fa07b3f7aa2421968c6f10d342d3f0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f04803a12135095c4a9a3df66d05198b0b89e876fc16c4cbb81b0dc00897b654 0.600000000000 1403855 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": 945549, "vin": [ { "gen": { "height": 945539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f04803a12135095c4a9a3df66d05198b0b89e876fc16c4cbb81b0dc00897b654" } } ], "extra": [ 1, 25, 226, 103, 2, 181, 71, 197, 29, 80, 177, 242, 208, 224, 82, 234, 128, 47, 31, 160, 123, 63, 122, 162, 66, 25, 104, 198, 241, 13, 52, 45, 63, 2, 17, 0, 0, 0, 3, 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