Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcdace24d928beffdd70e821c341c9356d7dc8c9c2669f0638fb76e934d11827

Tx prefix hash: 30ea35eefa2fdbb9f4caf700c9620323f172f05027413a8d54a60a05256b81ee
Tx public key: 92829402c0729f6b9a3e8bc2c412a7368a877336209000b81b65bf7698320c40
Timestamp: 1699828232 Timestamp [UCT]: 2023-11-12 22:30:32 Age [y:d:h:m:s]: 01:140:22:03:17
Block: 890334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361874 RingCT/type: yes/0
Extra: 0192829402c0729f6b9a3e8bc2c412a7368a877336209000b81b65bf7698320c4002110000000333af99f4000000000000000000

1 output(s) for total of 0.688579137000 dcy

stealth address amount amount idx
00: 416c230d94ccd573b8d55b6ffd9a120f06592d8164fe894a946298c638d741c5 0.688579137000 1346357 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": 890344, "vin": [ { "gen": { "height": 890334 } } ], "vout": [ { "amount": 688579137, "target": { "key": "416c230d94ccd573b8d55b6ffd9a120f06592d8164fe894a946298c638d741c5" } } ], "extra": [ 1, 146, 130, 148, 2, 192, 114, 159, 107, 154, 62, 139, 194, 196, 18, 167, 54, 138, 135, 115, 54, 32, 144, 0, 184, 27, 101, 191, 118, 152, 50, 12, 64, 2, 17, 0, 0, 0, 3, 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