Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f269688302cb4fb6b29d8d39d7a65391595e17f3ca39d45de69eff405aa7ab75

Tx prefix hash: e45768bc6ec42bbe4cdeea067910ab5d49ce8cd6cf5638c2da713490aa963563
Tx public key: db4b5153d7f0c75c4e38f56a39596d8bb4fac4b0f83ce943503a3fa0664d9c01
Timestamp: 1709499032 Timestamp [UCT]: 2024-03-03 20:50:32 Age [y:d:h:m:s]: 01:248:08:17:14
Block: 970508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436203 RingCT/type: yes/0
Extra: 01db4b5153d7f0c75c4e38f56a39596d8bb4fac4b0f83ce943503a3fa0664d9c010211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a5ed893b4182bdbdfd57ce5a3ba452242dee3bb481bdc5953fcf67f196bb128 0.600000000000 1430365 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": 970518, "vin": [ { "gen": { "height": 970508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a5ed893b4182bdbdfd57ce5a3ba452242dee3bb481bdc5953fcf67f196bb128" } } ], "extra": [ 1, 219, 75, 81, 83, 215, 240, 199, 92, 78, 56, 245, 106, 57, 89, 109, 139, 180, 250, 196, 176, 248, 60, 233, 67, 80, 58, 63, 160, 102, 77, 156, 1, 2, 17, 0, 0, 0, 4, 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