Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffd6890e5cb68648a2556eda806a27feaacac05e80292fb9fc57b83a083ed950

Tx prefix hash: 8c7c2ad4e2b178e2f640bd8dc53931749149400817af1d1d6579b920393cbd1a
Tx public key: a8e92234ad012dc7e5ac3f70a2349e923cc834580cc486985b734d477065f629
Timestamp: 1727591929 Timestamp [UCT]: 2024-09-29 06:38:49 Age [y:d:h:m:s]: 00:166:23:26:31
Block: 1120504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119140 RingCT/type: yes/0
Extra: 01a8e92234ad012dc7e5ac3f70a2349e923cc834580cc486985b734d477065f62902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6918d4c3fd4572e9f3ab2a5d3fc2f5cd702c016c7961b5517e825805ce6e352d 0.600000000000 1602443 of 15

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": 1120514, "vin": [ { "gen": { "height": 1120504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6918d4c3fd4572e9f3ab2a5d3fc2f5cd702c016c7961b5517e825805ce6e352d" } } ], "extra": [ 1, 168, 233, 34, 52, 173, 1, 45, 199, 229, 172, 63, 112, 162, 52, 158, 146, 60, 200, 52, 88, 12, 196, 134, 152, 91, 115, 77, 71, 112, 101, 246, 41, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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