Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bd3705ed412c26036bbd7116d6a69cfc6511e3f4a203269ba5607ec532d953c

Tx prefix hash: 10c1a00944344a1aff2a8dea4f081ef8648014bf11a8d2b19ca90baf9fd976f3
Tx public key: e308d9c6a695f4f8f6bad572640c13700b6dd5da91f8ce6824eb41805e36e07f
Timestamp: 1682345985 Timestamp [UCT]: 2023-04-24 14:19:45 Age [y:d:h:m:s]: 01:360:04:20:02
Block: 745632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518694 RingCT/type: yes/0
Extra: 01e308d9c6a695f4f8f6bad572640c13700b6dd5da91f8ce6824eb41805e36e07f021100000002b3164c24000000000000000000

1 output(s) for total of 2.076882213000 dcy

stealth address amount amount idx
00: c1fed59773eef205f8a5359cf613cb5965aa5c9ea57a851faa93e2abc2a36566 2.076882213000 1193101 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": 745642, "vin": [ { "gen": { "height": 745632 } } ], "vout": [ { "amount": 2076882213, "target": { "key": "c1fed59773eef205f8a5359cf613cb5965aa5c9ea57a851faa93e2abc2a36566" } } ], "extra": [ 1, 227, 8, 217, 198, 166, 149, 244, 248, 246, 186, 213, 114, 100, 12, 19, 112, 11, 109, 213, 218, 145, 248, 206, 104, 36, 235, 65, 128, 94, 54, 224, 127, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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