Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26b6583ecac8fc61ceaaa3b9c4192702f7294c18b86393de314db451c5051819

Tx prefix hash: 68b5b792e544acf4bccad4bcc7c0cd4acd0453c356545e843f4acb5f9188cc62
Tx public key: 18b5a2d1dc52ccfefcaf24c1d7dab293e727d5cfc29939609c1b6d85885cd413
Timestamp: 1702694278 Timestamp [UCT]: 2023-12-16 02:37:58 Age [y:d:h:m:s]: 01:186:09:45:05
Block: 914081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394263 RingCT/type: yes/0
Extra: 0118b5a2d1dc52ccfefcaf24c1d7dab293e727d5cfc29939609c1b6d85885cd41302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a803f810e8d59160bc5ce00a8507a722c257200f8cce3b8c562593899423a973 0.600000000000 1371363 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": 914091, "vin": [ { "gen": { "height": 914081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a803f810e8d59160bc5ce00a8507a722c257200f8cce3b8c562593899423a973" } } ], "extra": [ 1, 24, 181, 162, 209, 220, 82, 204, 254, 252, 175, 36, 193, 215, 218, 178, 147, 231, 39, 213, 207, 194, 153, 57, 96, 156, 27, 109, 133, 136, 92, 212, 19, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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