Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7e96a87e5eb776a92266215e469fb6098c65ea54023809d14a0c9483f2790bb

Tx prefix hash: aa232654784edd8550e643976f627379704a2ba986abddaed007e3f77f1ba83b
Tx public key: 381e5fd2f47e36160510aaf8a24a05ab6fa0f86928e60438f994d474acb11b1a
Timestamp: 1688728858 Timestamp [UCT]: 2023-07-07 11:20:58 Age [y:d:h:m:s]: 01:348:06:31:29
Block: 798561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509955 RingCT/type: yes/0
Extra: 01381e5fd2f47e36160510aaf8a24a05ab6fa0f86928e60438f994d474acb11b1a021100000005faf35c9c000000000000000000

1 output(s) for total of 1.386870916000 dcy

stealth address amount amount idx
00: 4ffb32e6ae79910834d9e325bb1a394beeb4a9ed13a2e4e64f99035d37ea4f34 1.386870916000 1249498 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": 798571, "vin": [ { "gen": { "height": 798561 } } ], "vout": [ { "amount": 1386870916, "target": { "key": "4ffb32e6ae79910834d9e325bb1a394beeb4a9ed13a2e4e64f99035d37ea4f34" } } ], "extra": [ 1, 56, 30, 95, 210, 244, 126, 54, 22, 5, 16, 170, 248, 162, 74, 5, 171, 111, 160, 248, 105, 40, 230, 4, 56, 249, 148, 212, 116, 172, 177, 27, 26, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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