Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cdbf1a73f4f965ac10c1df41cb9707ceb2fde6d52ab503ce491f965607b5131

Tx prefix hash: 1d6e10d04f30031f46ccf84e495c33a736bf079d70acde9cae160c15210963d3
Tx public key: 806c93007facc0fd2411d754b04256dbab7d58688c8d76b229d55bcb9fd712af
Timestamp: 1673443630 Timestamp [UCT]: 2023-01-11 13:27:10 Age [y:d:h:m:s]: 02:004:09:15:28
Block: 672444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525025 RingCT/type: yes/0
Extra: 01806c93007facc0fd2411d754b04256dbab7d58688c8d76b229d55bcb9fd712af0211000000048b7b6602000000000000000000

1 output(s) for total of 3.630060280000 dcy

stealth address amount amount idx
00: fb19ed57418caa2f596a8fd0f29c45bde9846f2c44e147c6e2ed1e68718a8b34 3.630060280000 1113987 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": 672454, "vin": [ { "gen": { "height": 672444 } } ], "vout": [ { "amount": 3630060280, "target": { "key": "fb19ed57418caa2f596a8fd0f29c45bde9846f2c44e147c6e2ed1e68718a8b34" } } ], "extra": [ 1, 128, 108, 147, 0, 127, 172, 192, 253, 36, 17, 215, 84, 176, 66, 86, 219, 171, 125, 88, 104, 140, 141, 118, 178, 41, 213, 91, 203, 159, 215, 18, 175, 2, 17, 0, 0, 0, 4, 139, 123, 102, 2, 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