Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26b3512d1cc11ca75ae6c0c3030cff13ee9da580981fb00beb1760db96ff0bd3

Tx prefix hash: dad31da6d2c24669c59db803bf90ac745201a74b61625bbe448e9a8a2da830c9
Tx public key: 45f85c7a158e332425c85e9685fd98b73f20f6255a06a2b6f3e5e8b1c3dd79dc
Timestamp: 1629107142 Timestamp [UCT]: 2021-08-16 09:45:42 Age [y:d:h:m:s]: 03:161:09:13:15
Block: 315213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 888551 RingCT/type: yes/0
Extra: 0145f85c7a158e332425c85e9685fd98b73f20f6255a06a2b6f3e5e8b1c3dd79dc021100000024e084ab86000000000000000000

1 output(s) for total of 55.408510131000 dcy

stealth address amount amount idx
00: 53921fa8567bd613f4acc8f024f40df924d651b916fbfe764d0e0eb15d8eb858 55.408510131000 656106 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": 315223, "vin": [ { "gen": { "height": 315213 } } ], "vout": [ { "amount": 55408510131, "target": { "key": "53921fa8567bd613f4acc8f024f40df924d651b916fbfe764d0e0eb15d8eb858" } } ], "extra": [ 1, 69, 248, 92, 122, 21, 142, 51, 36, 37, 200, 94, 150, 133, 253, 152, 183, 63, 32, 246, 37, 90, 6, 162, 182, 243, 229, 232, 177, 195, 221, 121, 220, 2, 17, 0, 0, 0, 36, 224, 132, 171, 134, 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