Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df68b83a8b4b5937f5fc3e5fa3382bb8e4e9490a1ec148eb676537e4c8906da0

Tx prefix hash: 8c0e09cbee9618cf76c5233303159212aa4099773fab2ecadced6a388f99205e
Tx public key: 810369b0e7b08ec9fc4572c75c680ab66cd9b64ee06dc1f400baf3e0c1b47aba
Timestamp: 1627985964 Timestamp [UCT]: 2021-08-03 10:19:24 Age [y:d:h:m:s]: 03:149:04:54:35
Block: 306455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 879345 RingCT/type: yes/0
Extra: 01810369b0e7b08ec9fc4572c75c680ab66cd9b64ee06dc1f400baf3e0c1b47aba02110000002337cb3088000000000000000000

1 output(s) for total of 59.241379987000 dcy

stealth address amount amount idx
00: 05e8354ab3643bfed1ab3cfd6a5fc0d6ca33112c81d41348dec37f90373c1fb0 59.241379987000 639044 of 0

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": 306465, "vin": [ { "gen": { "height": 306455 } } ], "vout": [ { "amount": 59241379987, "target": { "key": "05e8354ab3643bfed1ab3cfd6a5fc0d6ca33112c81d41348dec37f90373c1fb0" } } ], "extra": [ 1, 129, 3, 105, 176, 231, 176, 142, 201, 252, 69, 114, 199, 92, 104, 10, 182, 108, 217, 182, 78, 224, 109, 193, 244, 0, 186, 243, 224, 193, 180, 122, 186, 2, 17, 0, 0, 0, 35, 55, 203, 48, 136, 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