Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8f2e8cd80600f3f4f22e7e2be8e271d3cce76c9fec9947d17219f45add95695

Tx prefix hash: 5791e84e71586d5bbb96c8248fb0211da0881b667808845d2a39127891aa53ae
Tx public key: 3928a78d34aa90d01799fe7189c22994a1d6a5f36b6097d23617a8169a5ff9ea
Timestamp: 1699359758 Timestamp [UCT]: 2023-11-07 12:22:38 Age [y:d:h:m:s]: 01:149:16:38:00
Block: 886439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368170 RingCT/type: yes/0
Extra: 013928a78d34aa90d01799fe7189c22994a1d6a5f36b6097d23617a8169a5ff9ea02110000000133af99f4000000000000000000

1 output(s) for total of 0.709348440000 dcy

stealth address amount amount idx
00: 9f7bca3ad1ce178b409203838dd287824eed4874332a26c7ca807e2315fed1ed 0.709348440000 1342258 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": 886449, "vin": [ { "gen": { "height": 886439 } } ], "vout": [ { "amount": 709348440, "target": { "key": "9f7bca3ad1ce178b409203838dd287824eed4874332a26c7ca807e2315fed1ed" } } ], "extra": [ 1, 57, 40, 167, 141, 52, 170, 144, 208, 23, 153, 254, 113, 137, 194, 41, 148, 161, 214, 165, 243, 107, 96, 151, 210, 54, 23, 168, 22, 154, 95, 249, 234, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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