Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a211a5806d79093b25bd557fb1be77d0d41a6a288273dfee1eaf7545bd6a41c

Tx prefix hash: 10f4cb550bae695c8ac1ab921e451bacfda962d21462537e4598c5e0cc9c2658
Tx public key: 60c44a517046583b4c03ea5a3f06a5b5c81c1c518f6cf36ccf52296de4571dd0
Timestamp: 1707624753 Timestamp [UCT]: 2024-02-11 04:12:33 Age [y:d:h:m:s]: 00:350:23:50:10
Block: 954948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251037 RingCT/type: yes/0
Extra: 0160c44a517046583b4c03ea5a3f06a5b5c81c1c518f6cf36ccf52296de4571dd00211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edfd20a358e8ae8ababd669e0fa1d1304adab95e28604ff3160cd070b78d1f4a 0.600000000000 1414230 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": 954958, "vin": [ { "gen": { "height": 954948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edfd20a358e8ae8ababd669e0fa1d1304adab95e28604ff3160cd070b78d1f4a" } } ], "extra": [ 1, 96, 196, 74, 81, 112, 70, 88, 59, 76, 3, 234, 90, 63, 6, 165, 181, 200, 28, 28, 81, 143, 108, 243, 108, 207, 82, 41, 109, 228, 87, 29, 208, 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