Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90c31b023fd6aff3365d6530c3e1e0ccfb9ffa70fa9ef8cc64449c1227a120ee

Tx prefix hash: cce2b986aab03694a17c03723fbb9967caf32545ac3efa8975a56ba38d3fb610
Tx public key: a806958928707105b47f93992f950b8309c8dd79a1d39eb8e2c4cdf79e0b10a2
Timestamp: 1710570604 Timestamp [UCT]: 2024-03-16 06:30:04 Age [y:d:h:m:s]: 00:313:08:53:55
Block: 979406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224250 RingCT/type: yes/0
Extra: 01a806958928707105b47f93992f950b8309c8dd79a1d39eb8e2c4cdf79e0b10a20211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed524346fd1db9f2c95b0882ae36c8c7ce963bac5ba5b1bdebd68fb8b151fabc 0.600000000000 1439439 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": 979416, "vin": [ { "gen": { "height": 979406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed524346fd1db9f2c95b0882ae36c8c7ce963bac5ba5b1bdebd68fb8b151fabc" } } ], "extra": [ 1, 168, 6, 149, 137, 40, 112, 113, 5, 180, 127, 147, 153, 47, 149, 11, 131, 9, 200, 221, 121, 161, 211, 158, 184, 226, 196, 205, 247, 158, 11, 16, 162, 2, 17, 0, 0, 0, 5, 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