Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 821a162366706d9fecbf1ea0d9632691c840a18c71f7d61da2099d3d707d9eca

Tx prefix hash: bd8a338d5fcbf94ff754d7f2190e537d39c0d6dfd1816469a7a7ba1ab3416f48
Tx public key: 857f1fef2fc66c8e8983dbd101f9ba338c72cd9f97d21a237ef970199868ac2c
Timestamp: 1684156272 Timestamp [UCT]: 2023-05-15 13:11:12 Age [y:d:h:m:s]: 01:324:05:54:48
Block: 760644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492953 RingCT/type: yes/0
Extra: 01857f1fef2fc66c8e8983dbd101f9ba338c72cd9f97d21a237ef970199868ac2c021100000002b3164c24000000000000000000

1 output(s) for total of 1.852127402000 dcy

stealth address amount amount idx
00: db80dfa9d764f915972c77e42c1a317370190827b77e51e7e2c0472529950938 1.852127402000 1209273 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": 760654, "vin": [ { "gen": { "height": 760644 } } ], "vout": [ { "amount": 1852127402, "target": { "key": "db80dfa9d764f915972c77e42c1a317370190827b77e51e7e2c0472529950938" } } ], "extra": [ 1, 133, 127, 31, 239, 47, 198, 108, 142, 137, 131, 219, 209, 1, 249, 186, 51, 140, 114, 205, 159, 151, 210, 26, 35, 126, 249, 112, 25, 152, 104, 172, 44, 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